Heretic will crash if you activate a Wings of Wrath in your inventory while you already have another Wings of Wrath active. "Reference not set to an instance of an object" is dumped to stdout. I have run vavoom with -debug parameter, but have not found debug.txt anywhere...? edit - yes, i have write permissions on what i assume are all relevant folders

[quote="spiderman":1icyk2w8]I have run vavoom with -debug parameter, but have not found debug.txt anywhere...? edit - yes, i have write permissions on what i assume are all relevant folders It's very strange, since this file is written during all the vavoom session, not only in case of error. It should be loicated in vavoom/basev folder.

I can confirm the bug. debug.txt says

Log: >gimme artifacts
Log: YOU GOT IT
- (linespec.PowerFlight.EndEffect)
- RunFunction
- (linespec.PowerFlight.EndEffect 4)
- RunFunction
- (linespec.Powerup.Destroyed 1)
- VObject::ExecuteFunction
- (linespec.Powerup.Destroyed)
- VEntity::DestroyThinker
- RunFunction
- (engine.Thinker.Destroy 0)
- RunFunction
- (linespec.PowerupGiver.Use 102)
- RunFunction
- (linespec.EntityEx.UseInventory 21)
- RunFunction
- (svprogs.PlayerPawn.UseInventory 2)
- RunFunction
- (svprogs.Player.PlayerImpulse 230)
- RunFunction
- (svprogs.Player.PlayerTick 371)
- VObject::ExecuteFunction
- (svprogs.Player.PlayerTick)
- SV_RunClients
- SV_Ticker
- ServerFrame
- Host_Frame
Log: Doing C_Shutdown
Log: Doing CL_Shutdown
Log: PLAYER left the game

Log: Doing SV_Shutdown
Log: Doing delete GNet
Log: Doing delete GInput
Log: Doing V_Shutdown
Log: Doing delete GAudio
Log: Doing T_Shutdown
Log: Doing Sys_Shutdown
Log: Doing delete GSoundManager
Log: Doing R_ShutdownTexture
Log: Doing VCommand::Shutdown
Log: Doing VCvar::Shutdown
Log: Doing ShutdownMapInfo
Log: Doing FL_Shutdown
Log: Doing W_Shutdown
Log: Doing GLanguage.FreeData
Log: Doing VObject::StaticExit
Log: Doing VName::StaticExit
Uninitialised: Doing Z_Shutdown
Uninitialised: block 0x6ab508c size      660 at host.cpp:674
Uninitialised: block 0xb73b84 size        6 at str.cpp:108
Uninitialised: block 0x8b767c size      509 at sc_man.cpp:65
Uninitialised: block 0xb68a70 size       13 at str.cpp:108
Uninitialised: block 0xc5812c size       72 at lockdefs.cpp:186
Uninitialised: block 0xb6c92c size        6 at str.cpp:108
Uninitialised: block 0xb4e280 size      178 at sc_man.cpp:65
Uninitialised: block 0xb75690 size       13 at str.cpp:108
Uninitialised: block 0xc5823c size       72 at lockdefs.cpp:186
Uninitialised: 9 blocks allocated
STACK TRACE:

stack 0 0x570ef7 frame 0 0x7fffa6fb1b80


ERROR: Reference not set to an instance of an object

[quote="Crimson Wizard":29gwezx0][quote="spiderman":29gwezx0]I have run vavoom with -debug parameter, but have not found debug.txt anywhere...? edit - yes, i have write permissions on what i assume are all relevant folders It's very strange, since this file is written during all the vavoom session, not only in case of error. It should be loicated in vavoom/basev folder. I know, i've never been able to find the damn thing in any vavoom version i have run =/ would it be in ~/.vavoom/basev or the folder vavoom is compiled in (/usr/src/vavoom-svn/basev in my case)? Or am i looking in the wrong places?

[quote="spiderman":2kwvs6hk]I know, i've never been able to find the damn thing in any vavoom version i have run =/ would it be in ~/.vavoom/basev or the folder vavoom is compiled in (/usr/src/vavoom-svn/basev in my case)? Or am i looking in the wrong places? In Linux enviroments you should find it in ~/.vavoom/

$ ls -l ~/.vavoom/*.txt
-rw-r--r-- 1 davide users 2315 30 ago 13:56 /home/davide/.vavoom/debug.txt

Fixed.